LEGACY SERVER-ONLY FLOW VALIDATION
==================================

Target flow implemented:
Legacy campaign choice -> campaign video -> Create Multiplayer Game directly -> Create/Import Character -> export/save to selected account directory -> Ready -> Play in the same newly created multiplayer game.

Implementation checks:
- One BG2 process is launched for the multiplayer creation/lobby/play sequence.
- Before launch, BG2's normal characters folder is junctioned directly to the selected account's characters folder.
- No character files are copied by the launcher.
- No automatic character backup or restore was added.
- The launcher writes a one-shot `Drakhysys / Legacy Server Only = 1` setting to Baldur.lua.
- Supplied UI.MENU consumes the one-shot flag at START and opens CONNECTION_CREATE directly.
- Legacy server-only mode disables Join Game, Direct Connect, and session refresh controls.
- Create/Import Character, Ready and Play remain the stock BG2 multiplayer lobby/game path.
- UI.MENU is installed into the selected BaldurII.exe folder's override directory immediately before launch.
- CHARGEN import title is `IMPORT FROM MY ACCOUNT`.

Validation performed in build environment:
- account_launcher_core.py compiled successfully.
- account_campaign_launcher.py compiled successfully.
- test_account_campaign_launcher.py: 4 passed.
- Full GUI/no-backup test suite could not be collected in this Linux build environment because PySide6 is not installed here.
